Skip to main content
Logo, a drawing of a warm coffee vgagaleski

Back to all tags

test automation

Blogs

  • Writing Playwright tests can be incredibly rewarding, but like any tool, improper use can lead to frustrating results. Many developers, especially those transitioning from Selenium, inadvertently carry over practices that don't align with Playwright's capabilities. In this blog, we'll explore the most common mistakes made when writing Playwright tests and provide actionable tips to help you avoid them.

  • As teams adopt test automation, we often focus on writing tests, but overlook how to structure them for long-term maintainability. Just as we wouldn't build a house without proper architectural plans, we shouldn't build our test automation without a solid foundation. Whether you're a developer bringing your code organization expertise to testing, or an SDET looking for ideas on how to better structure your test project, this guide will provide several approaches and ideas on creating maintainable and scalable Playwright test framework.

  • Playwright 1.51 has just landed, and I'm excited about one standout feature the new "Copy prompt" button. While it appears as a simple addition to the Playwright report, this functionality can significantly boost reporting capabilities, shorten debugging time, and streamline error resolution. By creating a bridge between Playwright and language models, it opens the way for innovative features that could transform how we leverage AI and LLMs in our testing workflows. Let's explore what's new and discuss how this addition could benefit test automation going forward.

  • Imagine a test automation framework so powerful and versatile that it ignites a deep interest, making you eager to explore and understand every aspect of it. That's exactly what Playwright did for me. In a world filled with countless testing tools, Playwright stands out as a true game-changer, revolutionizing how we approach test automation.